Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.56%. Comparing base (e402833) to head (9c790d8).
Report is 18 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master    #9321   +/-   ##
=======================================
  Coverage   98.56%   98.56%           
=======================================
  Files         107      107           
  Lines       34896    34896           
  Branches     4135     4135           
=======================================
  Hits        34395    34395           
  Misses        334      334           
  Partials      167      167           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Backport to 3.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply a4b148e on top of patchback/backports/3.10/a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914/pr-9321

Backporting merged PR #9321 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.10/a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914/pr-9321 upstream/3.10

4. Now, cherry-pick PR Fix custom cookies example #9321 contents into that branch:

   $ git cherry-pick -x a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914

   If it'll yell at you with something like fatal: Commit a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix custom cookies example #9321 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914/pr-9321

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Backport to 3.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply a4b148e on top of patchback/backports/3.11/a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914/pr-9321

Backporting merged PR #9321 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.11/a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914/pr-9321 upstream/3.11

4. Now, cherry-pick PR Fix custom cookies example #9321 contents into that branch:

   $ git cherry-pick -x a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914

   If it'll yell at you with something like fatal: Commit a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix custom cookies example #9321 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/a4b148e84dacfaac3b17c6cb5f5ca3025b0e4914/pr-9321

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.